Brownout avoidance

ABSTRACT

Examples of the disclosure are directed to methods of managing power of various modules of an electronic device to prevent the voltage of the battery from falling to an undervoltage lockout (UVLO) threshold. In some examples, software operating on the electronic device or an associated electronic device (e.g., a paired electronic device) may assign power budgets to one or more modules, thereby preventing each module from drawing its maximum current capacity and causing the battery&#39;s voltage level to fall to the UVLO threshold. In some examples, a pre-UVLO threshold (i.e., a threshold higher than the UVLO threshold) may be used to modify the states of one or more modules to save power as the voltage of the battery approaches the UVLO threshold, but before the device must be fully powered off.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/812,904, filed Jul. 29, 2015 and published on Mar. 3, 2016 as U.S.Publication No. 2016-0064940; which claims the benefit under 35 U.S.C.§119(e) of U.S. Provisional Patent Application No. 62/042,172, filedAug. 26, 2014, the contents of which are incorporated by referenceherein in their entirety for all intended purposes.

FIELD OF THE DISCLOSURE

This relates generally to power management of an electronic device.

BACKGROUND OF THE DISCLOSURE

An electronic device may require a power supply, such as a battery.Further, the electronic device may require that the power supply have acertain minimum voltage in order to function properly. Accordingly, anelectronic device may monitor the voltage of its power supply, and powerdown the electronic device if the voltage falls to an undervoltagelockout (UVLO) threshold. This is known as a brownout, when power isstill available to the device, but the voltage is too low to functionproperly.

SUMMARY OF THE DISCLOSURE

An electronic device may require a power supply, such as a battery.Further, the electronic device may require that the power supply have acertain minimum voltage in order to function properly. Accordingly, anelectronic device may monitor the voltage of its power supply, and powerdown the electronic device if the voltage falls to an undervoltagelockout (UVLO) threshold. This is known as a brownout, when power isstill available to the device, but the voltage is too low to functionproperly. For example, if the voltage is already near the UVLOthreshold, and multiple modules draw power at once (e.g., speakers,Wi-Fi, and Bluetooth), electrical transients may cause the voltage tomomentarily fall below the UVLO threshold, thereby causing the device topower down.

Examples of the disclosure are directed to methods of managing the powerof various modules of the electronic device to prevent the voltage ofthe battery from falling to the undervoltage lockout (UVLO) threshold.In some examples, software operating on the electronic device or anassociated electronic device (e.g., a paired electronic device) mayassign power budgets to one or more modules, thereby preventing eachmodule from drawing its maximum current capacity and causing thebattery's voltage level to fall to the UVLO threshold. In some examples,a pre-UVLO threshold (i.e., a threshold higher than the UVLO threshold)may be used to modify the states of one or more modules to save power asthe voltage of the battery approaches the UVLO threshold, but before thedevice must be fully powered off. An electronic device may be anyelectronic device such as a desktop computer, portable multifunctiondevice (e.g., a smartphone), wearable device, tablet computer, etc. Insome examples, methods described herein may be useful for devices thathave relatively low battery capacity for a portable device. Further, themethods described herein may be particularly useful in cold temperatureconditions where battery impedance may be particularly problematic.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary method of assigning power budgets forfirst and second modules of an electronic device, according to examplesof the disclosure.

FIG. 2 illustrates an exemplary method of modifying a state of a modulebased on a pre-UVLO threshold, according to examples of the disclosure.

FIG. 3 is a block diagram illustrating an example of software andhardware interactions according to examples of the disclosure.

FIG. 4 illustrates an exemplary pre-UVLO signal according to examples ofthe disclosure.

FIG. 5 is a block diagram illustrating an exemplary API architecture,which may be used in some examples of the disclosure.

FIG. 6 illustrates an exemplary software stack of an API according toexamples of the disclosure.

FIG. 7 is a block diagram illustrating exemplary interactions betweenthe touch screen and other components of the device according toexamples of the disclosure.

FIG. 8 is a block diagram illustrating an example of a systemarchitecture that may be embodied within any portable or non-portabledevice according to examples of the disclosure.

DETAILED DESCRIPTION

In the following description of examples, reference is made to theaccompanying drawings which form a part hereof, and in which it is shownby way of illustration specific examples that can be practiced. It is tobe understood that other examples can be used and structural changes canbe made without departing from the scope of the disclosed examples.

An electronic device may require a power supply, such as a battery.Further, the electronic device may require that the power supply have acertain minimum voltage in order to function properly. Accordingly, anelectronic device may monitor the voltage of its power supply, and powerdown the electronic device if the voltage falls to an undervoltagelockout (UVLO) threshold. This is known as a brownout, when power isstill available to the device, but the voltage is too low to functionproperly. For example, if the voltage is already near the UVLOthreshold, and multiple modules draw power at once (e.g., speakers,Wi-Fi, and Bluetooth), electrical transients may cause the voltage tomomentarily fall below the UVLO threshold, thereby causing the device topower down.

Examples of the disclosure are directed to methods of managing the powerof various modules of the electronic device to prevent the voltage ofthe battery from falling to the undervoltage lockout (UVLO) threshold.In some examples, software operating on the electronic device or anassociated electronic device (e.g., a paired electronic device) mayassign power budgets to one or more modules, thereby preventing eachmodule from drawing its maximum current capacity and causing thebattery's voltage level to fall to the UVLO threshold. In some examples,a pre-UVLO threshold (i.e., a threshold higher than the UVLO threshold)may be used to modify the states of one or more modules to save power asthe voltage of the battery approaches the UVLO threshold, but before thedevice must be fully powered off. An electronic device may be anyelectronic device such as a desktop computer, portable multifunctiondevice (e.g., a smartphone), wearable device, tablet computer, etc. Insome examples, methods described herein may be useful for devices thathave relatively low battery capacity for a portable device. Further, themethods described herein may be particularly useful in cold temperatureconditions where battery impedance may be particularly problematic.

Although examples disclosed herein may be described and illustratedherein primarily in terms of an electronic device having a battery, itshould be understood that the examples are not so limited, but areadditionally applicable to devices including any kind of power supply,such as an alternating current (AC) power supply. Further, althoughexamples herein may be described and illustrated primarily in terms oftwo or three modules, it should be understood that the examples are notso limited, but are additionally applicable to an arbitrary number ofmodules.

FIG. 1 illustrates an exemplary method of assigning power budgets forfirst and second modules of an electronic device, according to examplesof the disclosure. The method may be performed at an electronic deviceincluding a plurality of modules (e.g., hardware peripherals such as aspeaker, microphone, Wi-Fi controller, Bluetooth, near fieldcommunication (NFC), accelerometer, gyroscope, magnetometer, globalpositioning system (GPS), central processing unit (CPU), graphicsprocessing unit (GPU), photoplethysmogram (PPG) sensor, heart ratemonitor, electrocardiogram (EKG) sensor, etc.).

A first power request for a first module of the plurality of modules(e.g., a request to allow the first module to draw its maximum currentcapacity or some percentage of its maximum current capacity) may bereceived (100). The request may come from the first module itself, aseparate electronic device (e.g., a paired device), or from softwarerequesting the use of the first module, among other possibilities.Further, a second power request for a second module of the plurality ofmodules may be received (102). Similarly, the second power request cancome from the second module, the paired device, or from softwarerequesting the use of the second module, among other possibilities.Power requests may be received by hardware or software components, suchas peak power manager 300 in FIG. 3.

A first power budget may be assigned (104) to the first module (e.g.,allowing the first module to draw some percentage of the first module'smaximum current capacity in accordance with the first power budget, orassigning a zero budget and/or denying the first power request). In someexamples, assigning the first power budget to the first module may bebased on a charge level of a battery of the electronic device (e.g., thefirst power budget may be reduced if the charge level is below athreshold level). In some examples, one or more predetermined budgetsmay be stored for a particular module, and assigning a budget mayinclude selecting one of the predetermined budgets. A power budget maybe assigned on a scale of 0-100 (e.g., as a percentage of the module'smaximum current capacity). A power budget may limit how much power themodule can draw at one time. That is, a module can cumulatively drawmore than its power budget, but the module's power draw at any givenmoment cannot exceed the budget. Power budgets may be assigned byhardware or software components, such as peak power manager 300 in FIG.3.

A second power budget may be assigned (106) to the second module basedon the first power budget (e.g., so that the current drawn by the firstand second modules does not peak to a level unsustainable by thebattery). For example, the second power budget may be assigned based ona rule that a total power budget (e.g., the sum of the first and secondpower budgets, and possibly additional power budgets) cannot exceed abudget limit. In some examples, the budget limit may be set at or underthe total power that can be safely drawn without triggering a brownoutcondition, and keeping the total power budget to the budget limit canthereby prevent any modules from triggering a brownout condition. Insome examples, a plurality of predetermined budgets may be stored forthe second module, and a relatively low budget may be selected for thesecond module based on the assigned budget for the first module.

In some examples, a first priority may be assigned to the first moduleand a second priority may be assigned to the second module, andassigning the second power budget may be further based on the first andsecond priorities (e.g., a module with a relatively high priority, suchas a speaker, may be assigned its requested budget, whereas a modulewith a relatively low priority, such as a GPS, may be assigned less thanits requested budget and/or its request may be denied). In someexamples, the first priority may be assigned with respect to aparticular functionality of the first module (e.g., differentfunctionalities of a module may have different priorities: a speaker mayhave a relatively low priority for playing a text message notificationand a relatively high priority for playing a telephone call ringtone).Priorities may be assigned by hardware or software components, such aspeak power manager 300 in FIG. 3.

In some examples, the first and/or second power budgets may be assignedbased on a determination of whether the device is in contact with a user(e.g., in a user's pocket, strapped to a user's arm, in the user's hand,etc.). Such a determination may be made based on light sensing, heatsensing, motion sensing, touch sensing, etc. If the device is not incontact with the user, then modules such as vibration/haptic feedbackmay be assigned a relatively low priority (e.g., because vibration is oflimited utility when the device is not in contact with a user).

In some examples, it may be determined that the first power request isassociated with a user-initiated task, and the first priority may beassigned based on the determination that the first power request isassociated with a user-initiated task (e.g., a user-initiated task maybe given a higher priority than an automated task; the speaker may begiven a relatively high priority when the user requests that music beplayed, whereas the Wi-Fi controller may be given a relatively lowpriority when it is being used to automatically check for app updates inthe background).

In some examples, the first power budget may be reduced based on adetermination that the second priority is higher than the first priority(e.g., a module with a relatively high priority may effectively takepower budget away from a module with a relatively low priority that hasalready been assigned a power budget). In some examples, reducing thefirst power budget may include notifying the first module that the firstpower budget has been revoked, and reducing power to the first module(or powering off the first module), wherein the second power budget maybe assigned only after the power to the first module has been reduced(or powered off). Power budgets may be modified (reduced, revoked,increased, etc.) by hardware or software components, such as peak powermanager 300 in FIG. 3.

Power may be drawn (108) at the first module based on the first powerbudget and at the second module based on the second power budget (e.g.,drawing current at a level no higher than the budgeted level).

In some examples, a third power request for a third module of theplurality of modules may be received. The third power request may bedenied based on the first and second power budgets (e.g., based on arule that the third module cannot run while the first and second modulesdraw power at the first and second power budgets, and/or based onpriorities of the first and second modules being higher than a priorityof the third module).

In some examples, certain combinations of modules may be excluded, andbudgets may be assigned accordingly. For example, a power request for aGPS (e.g., a relatively low priority module) may be denied based onbudgets being already assigned to a speaker and a Wi-Fi controller(e.g., relatively high priority modules). In some examples, if budgetsare already assigned to a Wi-Fi controller and a GPS, and a powerrequest is made for a speaker, the budget assigned to the GPS may berevoked and the power request to the speaker may be granted.

In some examples, the electronic device may include a power supply(e.g., a battery). A first characteristic of the power supply (e.g., avoltage level, a charge level of a battery, etc.) may be obtained, andit may be determined that the first characteristic is lower than a firstthreshold (e.g., a UVLO threshold or threshold higher than the UVLOthreshold). The first power budget may be assigned to the first modulebased on the determination that the first characteristic is lower thanthe first threshold (e.g., assigning a relatively lower power budgetand/or reducing a power budget because the first characteristic is lowerthan the first threshold; a relatively low priority module may have areduced power budget if the first characteristic is lower than the firstthreshold; etc.). In some examples, the first power budget may beassigned to the first module based on the relationship between the firstcharacteristic and the first threshold over time (e.g., assigning arelatively low power budget and/or reducing a power budget if the firstcharacteristic is frequently lower the first threshold, or if the firstcharacteristic is lower than the first threshold for at least a setduration of time).

In some examples, power budgets are assigned to respective modules inresponse to a first module requesting power. In such a case, a budgetmay be assigned to the first module requesting power, and/or a secondmodule may have a budget assigned/adjusted/revoked in response to thefirst module requesting power (e.g., if the second module's budget needsto be lowered or revoked to accommodate the first module's power draw).

In some examples, power budgets may be assigned or adjusted in responseto events other than power requests. For example, power budgets may beadjusted in response to changes in battery level (e.g., one or morebudgets may be reduced in response to a battery level falling beneath athreshold level), in response to changes in charging state (e.g., one ormore budgets may be increased when the device's battery is beingcharged), and/or in response to elapsed time (e.g., budgets may beperiodically adjusted or re-determined every two hours).

FIG. 2 illustrates an exemplary method of modifying a state of a modulebased on a pre-UVLO threshold, according to examples of the disclosure.The method may be performed at an electronic device including a powersupply (e.g., a battery) and a first module (e.g., a hardware peripheralsuch as a speaker, microphone, Wi-Fi controller, Bluetooth, near fieldcommunication (NFC), accelerometer, gyroscope, magnetometer, GPS, etc.).

A voltage level of the power supply may be obtained (201), and it may bedetermined that the voltage level is lower than a first threshold (203).For example, the first threshold may be a pre-UVLO threshold (e.g., 3.8V), higher than the UVLO threshold (e.g., 3.5 V). The voltage level maybe compared to the first threshold by hardware or software componentssuch as power management unit 312, as illustrated in FIG. 3.

In accordance with a determination that the voltage level is lower thanthe first threshold, a state of the first module may be modified (205)(e.g., turning off the first module, changing a mode of the firstmodule, etc., so as to prevent the module's usage from pushing thevoltage level of the power supply below an undervoltage lockout (UVLO)threshold). In some examples, modifying the state may include preventingthe first module from drawing power for a predefined period of time(e.g., stopping the Wi-Fi radio for 20-40 ms, or some other time periodlong enough for a peak current to cease, among other possibilities). Insome examples, modifying the state may include changing a mode of thefirst module for a predefined period of time (e.g., throttling the CPUclock, reducing a core voltage of the CPU, and disabling one or morefeatures of a sensor, among other possibilities). In some examples, oneor more power budgets may be assigned or modified (e.g., reduced) basedon a determination that the voltage level is lower than the firstthreshold. Modifying the state of one or more components and/orassigning and modifying power budgets may be performed by hardware orsoftware components, such as power management unit 312 and/or peak powermanager 300, as illustrated in FIG. 3.

In some examples, it may be determined that the voltage level is lowerthan a second threshold (e.g., an undervoltage lockout (UVLO)threshold), lower than the first threshold. In accordance with adetermination that the voltage level is lower than the second threshold,the device may be powered off.

In some examples, the state of the first module may remain modified fora predetermined period of time or until the voltage level is above athird threshold (e.g., higher than the first threshold) for thepredetermined period of time. After the voltage level is above the thirdthreshold for the predetermined period of time, the state of the firstmodule may be modified back (e.g., turning on the first module,unthrottling the CPU clock, increasing the core voltage of the CPU,enabling one or more features of a sensor, etc.).

FIG. 3 is a block diagram illustrating an example of software andhardware interactions (such as the methods described with reference toFIGS. 1 and 2) according to examples of the disclosure. Each blockand/or each connection between the blocks in FIG. 3 may represent one ormore hardware or software modules.

Peak power manager 300 may receive power requests from one or moremodules, such as Wi-Fi 304, speaker 306, sensors 308, NFC 310, CPU 316,and GPU 318. The peak power manager 300 may assign/modify budgets forthe one or more modules, and accept, deny, or revoke the power requestsreceived from the modules. Each module 304, 306, 308, 310, 316, and 318may receive its assigned budget from the peak power manager 300. Thepeak power manager 300 may store in a computer-readable medium thebudgets assigned to each module, state information for each module,priorities for each module, etc.

In some examples, a power management unit 312 may monitor the voltagelevel of a power supply 314 and compare the voltage level to a pre-UVLOthreshold and/or a UVLO threshold. The power management unit 312 maythen modify the state of one or more modules (e.g., by throttling theCPU 316 or the GPU 318, etc.) in accordance with a determination thatthe voltage level has dropped below the pre-UVLO threshold. In someexamples, the power management unit 312 may notify the peak powermanager 300 that voltage level has dropped below the pre-UVLO threshold(e.g., by sending a pre-UVLO signal as described with reference to FIG.4), and the peak power manager may assign/modify one or more budgets inaccordance (e.g., a power budget for a low priority module may bereduced or revoked in response to a determination that voltage level hasdropped below the pre-UVLO threshold).

In some examples, the power management unit 312 in FIG. 3 may have avoltage comparator detecting pre-UVLO conditions (e.g., based ondetection of a voltage level of the power supply 314 dropping below apre-UVLO threshold voltage). The output signal generated by the powermanagement unit voltage comparator in FIG. 3 may be observed as a pulsedsignal and recorded by the peak power manager 300. In some examples, thepeak power manager can use hardware assistance from a pulse widthmodulator (PWM) device used as an input signal monitoring device,accounting for the time the input signal is set at high or low level.For example, the PWM device might increment a counter when the signal isat high level, switch to another time counter when the signal switchesto low level. The PWM device might also have the ability to generateinterrupts to the peak power manager when the signal transitions to highor low level or when the signal is asserted at high or low level for agiven time above a certain threshold.

FIG. 4 illustrates an exemplary pre-UVLO signal according to examples ofthe disclosure. The pre-UVLO signal may drop to zero for as long as thevoltage level of the power supply 314 is below the pre-UVLO thresholdvoltage. For example, in FIG. 4, the voltage level of the power supplyhas dropped below the pre-UVLO threshold voltage three times, Δt₁, Δt₂,and Δt₃. As described with reference to FIG. 2, hardware mitigation maybe engaged at the first detection of the voltage level falling below thepre-UVLO threshold voltage. However, the duration of each voltage dropmay be monitored, and software mitigation (e.g., adjusting softwarebudgets as described with reference to FIG. 1) may be engaged inresponse to the duration of a voltage drop exceeding a predeterminedthreshold duration. For example, the first two voltage drops in FIG. 4,Δt₁ and Δt₂, are relatively short compared to Δt₃. If Δt₃ exceeds apredetermined threshold duration, then one or more module budgets may beadjusted (e.g., drastically reduced) in an attempt to bring the voltagelevel of the power supply back up above the pre-UVLO threshold voltage.In some examples, each power drop At may be categorized based on itsduration (e.g., short (0-100 ms), moderate (100-200 ms), long (at least200 ms), etc.), and software mitigation may be engaged in response todetection of a certain number of voltage drops in a particular category.For example, software mitigation may be engaged in response to three ormore voltage drops categorized as long (e.g., voltage drops lasting atleast 200 ms).

In some examples, the methods described herein may be used to enablespecific use cases of an electronic device. For example, it may be moreimportant for a user to hear a telephone call ringtone than a shortmessage service (SMS) notification. Accordingly, the speaker module mayhave a higher priority for a ringtone than for an SMS notification.Further, these priorities may result in a ringtone power request gettinga higher budget than an SMS notification power request. As a result, theringtone may be played louder by the speaker than the SMS notificationdue to the ringtone having more available power in its budget.

In another example, many applications stream media (e.g., audio orvideo) over Wi-Fi and play back the media over a speaker. Accordingly,it may be important to assign budgets in such a way that Wi-Fi and mediaplay back can happen concurrently (e.g., both modules may be assignedhigh priorities and other modules may receive relatively low budgets asa result). Further, haptic feedback when typing may be an essential partof a virtual keyboard in a media streaming application, and thus budgetsmay need to be assigned so that all three of these functionalities(haptic feedback, Wi-Fi, speaker) can be performed concurrently.

The examples discussed above can be implemented in one or moreApplication Programming Interfaces (APIs). An API is an interfaceimplemented by a program code component or hardware component(hereinafter “API-implementing component”) that allows a differentprogram code component or hardware component (hereinafter “API-callingcomponent”) to access and use one or more functions, methods,procedures, data structures, classes, and/or other services provided bythe API-implementing component. An API can define one or more parametersthat are passed between the API-calling component and theAPI-implementing component.

The above-described features can be implemented as part of anapplication program interface (API) that can allow it to be incorporatedinto different applications (e.g., spreadsheet apps) utilizing touchinput as an input mechanism. An API can allow a developer of anAPI-calling component (which may be a third party developer) to leveragespecified features, such as those described above, provided by anAPI-implementing component. There may be one API-calling component orthere may be more than one such component. An API can be a source codeinterface that a computer system or program library provides in order tosupport requests for services from an application. An operating system(OS) can have multiple APIs to allow applications running on the OS tocall one or more of those APIs, and a service (such as a programlibrary) can have multiple APIs to allow an application that uses theservice to call one or more of those APIs. An API can be specified interms of a programming language that can be interpreted or compiled whenan application is built.

In some examples, the API-implementing component may provide more thanone API, each providing a different view of the functionalityimplemented by the API-implementing component, or with different aspectsthat access different aspects of the functionality implemented by theAPI-implementing component. For example, one API of an API-implementingcomponent can provide a first set of functions and can be exposed tothird party developers, and another API of the API-implementingcomponent can be hidden (not exposed) and provide a subset of the firstset of functions and also provide another set of functions, such astesting or debugging functions which are not in the first set offunctions. In other examples the API-implementing component may itselfcall one or more other components via an underlying API and thus be bothan API-calling component and an API-implementing component.

An API defines the language and parameters that API-calling componentsuse when accessing and using specified features of the API-implementingcomponent. For example, an API-calling component accesses the specifiedfeatures of the API-implementing component through one or more API callsor invocations (embodied for example by function or method calls)exposed by the API and passes data and control information usingparameters via the API calls or invocations. The API-implementingcomponent may return a value through the API in response to an API callfrom an API-calling component. While the API defines the syntax andresult of an API call (e.g., how to invoke the API call and what the APIcall does), the API may not reveal how the API call accomplishes thefunction specified by the API call. Various API calls are transferredvia the one or more application programming interfaces between thecalling (API-calling component) and an API-implementing component.Transferring the API calls may include issuing, initiating, invoking,calling, receiving, returning, or responding to the function calls ormessages; in other words, transferring can describe actions by either ofthe API-calling component or the API-implementing component. Thefunction calls or other invocations of the API may send or receive oneor more parameters through a parameter list or other structure. Aparameter can be a constant, key, data structure, object, object class,variable, data type, pointer, array, list or a pointer to a function ormethod or another way to reference a data or other item to be passed viathe API.

Furthermore, data types or classes may be provided by the API andimplemented by the API-implementing component. Thus, the API-callingcomponent may declare variables, use pointers to, use or instantiateconstant values of such types or classes by using definitions providedin the API.

Generally, an API can be used to access a service or data provided bythe API-implementing component or to initiate performance of anoperation or computation provided by the API-implementing component. Byway of example, the API-implementing component and the API-callingcomponent may each be any one of an operating system, a library, adevice driver, an API, an application program, or other module (itshould be understood that the API-implementing component and theAPI-calling component may be the same or different type of module fromeach other). API-implementing components may in some cases be embodiedat least in part in firmware, microcode, or other hardware logic. Insome examples, an API may allow a client program to use the servicesprovided by a Software Development Kit (SDK) library. In other examplesan application or other client program may use an API provided by anApplication Framework. In these examples the application or clientprogram may incorporate calls to functions or methods provided by theSDK and provided by the API or use data types or objects defined in theSDK and provided by the API. An Application Framework may in theseexamples provide a main event loop for a program that responds tovarious events defined by the Framework. The API allows the applicationto specify the events and the responses to the events using theApplication Framework. In some implementations, an API call can reportto an application the capabilities or state of a hardware device,including those related to aspects such as input capabilities and state,output capabilities and state, processing capability, power state,storage capacity and state, communications capability, etc., and the APImay be implemented in part by firmware, microcode, or other low levellogic that executes in part on the hardware component.

The API-calling component may be a local component (i.e., on the samedata processing system as the API-implementing component) or a remotecomponent (i.e., on a different data processing system from theAPI-implementing component) that communicates with the API-implementingcomponent through the API over a network. It should be understood thatan API-implementing component may also act as an API-calling component(i.e., it may make API calls to an API exposed by a differentAPI-implementing component) and an API-calling component may also act asan API-implementing component by implementing an API that is exposed toa different API-calling component.

The API may allow multiple API-calling components written in differentprogramming languages to communicate with the API-implementing component(thus the API may include features for translating calls and returnsbetween the API-implementing component and the API-calling component);however the API may be implemented in terms of a specific programminglanguage. An API-calling component can, in one example, call APIs fromdifferent providers such as a set of APIs from an OS provider andanother set of APIs from a plug-in provider and another set of APIs fromanother provider (e.g. the provider of a software library) or creator ofthe another set of APIs.

FIG. 5 is a block diagram illustrating an exemplary API architecture,which may be used in some examples of the disclosure. As shown in FIG.5, the API architecture 600 includes the API-implementing component 610(e.g., an operating system, a library, a device driver, an API, anapplication program, software or other module) that implements the API620. The API 620 specifies one or more functions, methods, classes,objects, protocols, data structures, formats and/or other features ofthe API-implementing component that may be used by the API-callingcomponent 630. The API 620 can specify at least one calling conventionthat specifies how a function in the API-implementing component receivesparameters from the API-calling component and how the function returns aresult to the API-calling component. The API-calling component 630(e.g., an operating system, a library, a device driver, an API, anapplication program, software or other module), makes API calls throughthe API 620 to access and use the features of the API-implementingcomponent 610 that are specified by the API 620. The API-implementingcomponent 610 may return a value through the API 620 to the API-callingcomponent 630 in response to an API call.

It will be appreciated that the API-implementing component 610 mayinclude additional functions, methods, classes, data structures, and/orother features that are not specified through the API 620 and are notavailable to the API-calling component 630. It should be understood thatthe API-calling component 630 may be on the same system as theAPI-implementing component 610 or may be located remotely and accessesthe API-implementing component 610 using the API 620 over a network.While FIG. 5 illustrates a single API-calling component 630 interactingwith the API 620, it should be understood that other API-callingcomponents, which may be written in different languages (or the samelanguage) than the API-calling component 630, may use the API 620.

The API-implementing component 610, the API 620, and the API-callingcomponent 630 may be stored in a non-transitory machine-readable storagemedium, which includes any mechanism for storing information in a formreadable by a machine (e.g., a computer or other data processingsystem). For example, a machine-readable medium includes magnetic disks,optical disks, random access memory; read only memory, flash memorydevices, etc.

In the exemplary software stack shown in FIG. 6, applications can makecalls to Services A or B using several Service APIs and to OperatingSystem (OS) using several OS APIs. Services A and B can make calls to OSusing several OS APIs.

Note that the Service 2 has two APIs, one of which (Service 2 API 1)receives calls from and returns values to Application 1 and the other(Service 2 API 2) receives calls from and returns values to Application2. Service 1 (which can be, for example, a software library) makes callsto and receives returned values from OS API 1, and Service 2 (which canbe, for example, a software library) makes calls to and receivesreturned values from both OS API 1 and OS API 2. Application 2 makescalls to and receives returned values from OS API 2.

FIG. 7 is a block diagram illustrating exemplary interactions betweenthe touch screen and the other components of the device. Describedexamples may include touch I/O device 1001 that can receive touch inputfor interacting with computing system 1003 via wired or wirelesscommunication channel 1002. Touch I/O device 1001 may be used to provideuser input to computing system 1003 in lieu of or in combination withother input devices such as a keyboard, mouse, etc. One or more touchI/O devices 1001 may be used for providing user input to computingsystem 1003. Touch I/O device 1001 may be an integral part of computingsystem 1003 (e.g., touch screen on a smartphone or a tablet PC) or maybe separate from computing system 1003.

Touch I/O device 1001 may include a touch sensing panel which is whollyor partially transparent, semitransparent, non-transparent, opaque orany combination thereof. Touch I/O device 1001 may be embodied as atouch screen, touch pad, a touch screen functioning as a touch pad(e.g., a touch screen replacing the touchpad of a laptop), a touchscreen or touchpad combined or incorporated with any other input device(e.g., a touch screen or touchpad disposed on a keyboard) or anymulti-dimensional object having a touch sensing surface for receivingtouch input.

In one example, touch I/O device 1001 embodied as a touch screen mayinclude a transparent and/or semitransparent touch sensing panelpartially or wholly positioned over at least a portion of a display.According to this example, touch I/O device 1001 functions to displaygraphical data transmitted from computing system 1003 (and/or anothersource) and also functions to receive user input. In other examples,touch I/O device 1001 may be embodied as an integrated touch screenwhere touch sensing components/devices are integral with displaycomponents/devices. In still other examples a touch screen may be usedas a supplemental or additional display screen for displayingsupplemental or the same graphical data as a primary display and toreceive touch input.

Touch I/O device 1001 may be configured to detect the location of one ormore touches or near touches on device 1001 based on capacitive,resistive, optical, acoustic, inductive, mechanical, chemicalmeasurements, or any phenomena that can be measured with respect to theoccurrences of the one or more touches or near touches in proximity todevice 1001. Software, hardware, firmware or any combination thereof maybe used to process the measurements of the detected touches to identifyand track one or more gestures. A gesture may correspond to stationaryor non-stationary, single or multiple, touches or near touches on touchI/O device 1001. A gesture may be performed by moving one or morefingers or other objects in a particular manner on touch I/O device 1001such as tapping, pressing, rocking, scrubbing, twisting, changingorientation, pressing with varying pressure and the like at essentiallythe same time, contiguously, or consecutively. A gesture may becharacterized by, but is not limited to a pinching, sliding, swiping,rotating, flexing, dragging, or tapping motion between or with any otherfinger or fingers. A single gesture may be performed with one or morehands, by one or more users, or any combination thereof.

Computing system 1003 may drive a display with graphical data to displaya graphical user interface (GUI). The GUI may be configured to receivetouch input via touch I/O device 1001. Embodied as a touch screen, touchI/O device 1001 may display the GUI. Alternatively, the GUI may bedisplayed on a display separate from touch I/O device 1001. The GUI mayinclude graphical elements displayed at particular locations within theinterface. Graphical elements may include but are not limited to avariety of displayed virtual input devices including virtual scrollwheels, a virtual keyboard, virtual knobs, virtual buttons, any virtualUI, and the like. A user may perform gestures at one or more particularlocations on touch I/O device 1001 which may be associated with thegraphical elements of the GUI. In other examples, the user may performgestures at one or more locations that are independent of the locationsof graphical elements of the GUI. Gestures performed on touch I/O device1001 may directly or indirectly manipulate, control, modify, move,actuate, initiate or generally affect graphical elements such ascursors, icons, media files, lists, text, all or portions of images, orthe like within the GUI. For instance, in the case of a touch screen, auser may directly interact with a graphical element by performing agesture over the graphical element on the touch screen. Alternatively, atouch pad generally provides indirect interaction. Gestures may alsoaffect non-displayed GUI elements (e.g., causing user interfaces toappear) or may affect other actions within computing system 1003 (e.g.,affect a state or mode of a GUI, application, or operating system).Gestures may or may not be performed on touch I/O device 1001 inconjunction with a displayed cursor. For instance, in the case in whichgestures are performed on a touchpad, a cursor (or pointer) may bedisplayed on a display screen or touch screen and the cursor may becontrolled via touch input on the touchpad to interact with graphicalobjects on the display screen. In other examples in which gestures areperformed directly on a touch screen, a user may interact directly withobjects on the touch screen, with or without a cursor or pointer beingdisplayed on the touch screen.

Feedback may be provided to the user via communication channel 1002 inresponse to or based on the touch or near touches on touch I/O device1001. Feedback may be transmitted optically, mechanically, electrically,olfactory, acoustically, or the like or any combination thereof and in avariable or non-variable manner.

Attention is now directed towards examples of a system architecture thatmay be embodied within any portable or non-portable device including butnot limited to a communication device (e.g. mobile phone, smart phone),a multi-media device (e.g., MP3 player, TV, radio), a portable orhandheld computer (e.g., tablet, netbook, laptop), a desktop computer,an All-In-One desktop, a peripheral device, or any other system ordevice adaptable to the inclusion of system architecture 2000, includingcombinations of two or more of these types of devices. FIG. 8 is a blockdiagram of one example of system 2000 that generally includes one ormore computer-readable mediums 2001, processing system 2004, I/Osubsystem 2006, radio frequency (RF) circuitry 2008, audio circuitry2010, and sensors circuitry 2011. These components may be coupled by oneor more communication buses or signal lines 2003.

It should be apparent that the architecture shown in FIG. 8 is only oneexample architecture of system 2000, and that system 2000 could havemore or fewer components than shown, or a different configuration ofcomponents. The various components shown in FIG. 8 can be implemented inhardware, software, firmware or any combination thereof, including oneor more signal processing and/or application specific integratedcircuits.

RF circuitry 2008 can be used to send and receive information over awireless link or network to one or more other devices and includeswell-known circuitry for performing this function. RF circuitry 2008 andaudio circuitry 2010 can be coupled to processing system 2004 viaperipherals interface 2016. Interface 2016 can include various knowncomponents for establishing and maintaining communication betweenperipherals and processing system 2004. Audio circuitry 2010 can becoupled to audio speaker 2050 and microphone 2052 and can include knowncircuitry for processing voice signals received from interface 2016 toenable a user to communicate in real-time with other users. In someexamples, audio circuitry 2010 can include a headphone jack (not shown).Sensors circuitry 2011 can be coupled to various sensors including, butnot limited to, one or more Light Emitting Diodes (LEDs) or other lightemitters, one or more photodiodes or other light sensors, one or morephotothermal sensors, a magnetometer, an accelerometer, a gyroscope, abarometer, a compass, a proximity sensor, a camera, an ambient lightsensor, a thermometer, a GPS sensor, and various system sensors whichcan sense remaining battery life, power consumption, processor speed,CPU load, and the like.

Peripherals interface 2016 can couple the input and output peripheralsof the system to processor 2018 and computer-readable medium 2001. Oneor more processors 2018 communicate with one or more computer-readablemediums 2001 via controller 2020. Computer-readable medium 2001 can beany device or medium that can store code and/or data for use by one ormore processors 2018. In some examples, medium 2001 can be anon-transitory computer-readable storage medium. Medium 2001 can includea memory hierarchy, including but not limited to cache, main memory andsecondary memory. The memory hierarchy can be implemented using anycombination of RAM (e.g., SRAM, DRAM, DDRAM), ROM, FLASH, magneticand/or optical storage devices, such as disk drives, magnetic tape, CDs(compact disks) and DVDs (digital video discs). Medium 2001 may alsoinclude a transmission medium for carrying information-bearing signalsindicative of computer instructions or data (with or without a carrierwave upon which the signals are modulated). For example, thetransmission medium may include a communications network, including butnot limited to the Internet (also referred to as the World Wide Web),intranet(s), Local Area Networks (LANs), Wide Local Area Networks(WLANs), Storage Area Networks (SANs), Metropolitan Area Networks (MAN)and the like.

One or more processors 2018 can run various software components storedin medium 2001 to perform various functions for system 2000. In someexamples, the software components can include operating system 2022,communication module (or set of instructions) 2024, touch processingmodule (or set of instructions) 2026, graphics module (or set ofinstructions) 2028, and one or more applications (or set ofinstructions) 2030. Each of these modules and above noted applicationscan correspond to a set of instructions for performing one or morefunctions described above and the methods described in this application(e.g., the computer-implemented methods and other information processingmethods described herein). These modules (i.e., sets of instructions)need not be implemented as separate software programs, procedures ormodules, and thus various subsets of these modules may be combined orotherwise re-arranged in various examples. In some examples, medium 2001may store a subset of the modules and data structures identified above.Furthermore, medium 2001 may store additional modules and datastructures not described above.

Operating system 2022 can include various procedures, sets ofinstructions, software components and/or drivers for controlling andmanaging general system tasks (e.g., memory management, storage devicecontrol, power management, etc.) and facilitates communication betweenvarious hardware and software components.

Communication module 2024 can facilitate communication with otherdevices over one or more external ports 2036 or via RF circuitry 2008and can include various software components for handling data receivedfrom RF circuitry 2008 and/or external port 2036.

Graphics module 2028 can include various known software components forrendering, animating and displaying graphical objects on a displaysurface. In examples in which touch I/O device 2012 is a touch sensingdisplay (e.g., touch screen), graphics module 2028 can includecomponents for rendering, displaying, and animating objects on the touchsensing display.

One or more applications 2030 can include any applications installed onsystem 2000, including without limitation, a browser, address book,contact list, email, instant messaging, word processing, keyboardemulation, widgets, JAVA-enabled applications, encryption, digitalrights management, voice recognition, voice replication, locationdetermination capability (such as that provided by the globalpositioning system (GPS)), a music player, etc.

Touch processing module 2026 can include various software components forperforming various tasks associated with touch I/O device 2012 includingbut not limited to receiving and processing touch input received fromI/O device 2012 via touch I/O device controller 2032.

I/O subsystem 2006 can be coupled to touch I/O device 2012 and one ormore other I/O devices 2014 for controlling or performing variousfunctions. Touch I/O device 2012 can communicate with processing system2004 via touch I/O device controller 2032, which can include variouscomponents for processing user touch input (e.g., scanning hardware).One or more other input controllers 2034 can receive/send electricalsignals from/to other I/O devices 2014. Other I/O devices 2014 mayinclude physical buttons, dials, slider switches, sticks, keyboards,touch pads, additional display screens, or any combination thereof.

If embodied as a touch screen, touch I/O device 2012 can display visualoutput to the user in a GUI. The visual output may include text,graphics, video, and any combination thereof. Some or all of the visualoutput may correspond to user-interface objects. Touch I/O device 2012can form a touch sensing surface that accepts touch input from the user.Touch I/O device 2012 and touch screen controller 2032 (along with anyassociated modules and/or sets of instructions in medium 2001) candetect and track touches or near touches (and any movement or release ofthe touch) on touch I/O device 2012 and can convert the detected touchinput into interaction with graphical objects, such as one or moreuser-interface objects. In the case in which device 2012 is embodied asa touch screen, the user can directly interact with graphical objectsthat are displayed on the touch screen. Alternatively, in the case inwhich device 2012 is embodied as a touch device other than a touchscreen (e.g., a touch pad), the user may indirectly interact withgraphical objects that are displayed on a separate display screenembodied as I/O device 2014.

Touch I/O device 2012 may be analogous to the multi-touch sensingsurface described in the following U.S. Pat. No. 6,323,846 (Westerman etal.), No. 6,570,557 (Westerman et al.), and/or No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference.

In examples for which touch I/O device 2012 is a touch screen, the touchscreen may use LCD (liquid crystal display) technology, LPD (lightemitting polymer display) technology, OLED (organic LED), or OEL(organic electro luminescence), although other display technologies maybe used in other examples.

Feedback may be provided by touch I/O device 2012 based on the user'stouch input as well as a state or states of what is being displayedand/or of the computing system. Feedback may be transmitted optically(e.g., light signal or displayed image), mechanically (e.g., hapticfeedback, touch feedback, force feedback, or the like), electrically(e.g., electrical stimulation), olfactory, acoustically (e.g., beep orthe like), or the like or any combination thereof and in a variable ornon-variable manner.

System 2000 can also include power system 2044 for powering the varioushardware components and may include a power management system, one ormore power sources, a recharging system, a power failure detectioncircuit, a power converter or inverter, a power status indicator and anyother components typically associated with the generation, managementand distribution of power in portable devices.

In some examples, peripherals interface 2016, one or more processors2018, and memory controller 2020 may be implemented on a single chip,such as processing system 2004. In some other examples, they may beimplemented on separate chips.

Examples of the disclosure can be advantageous in preventing a devicefrom reaching its UVLO threshold and powering off, thereby allowing thedevice to be used for a longer period of time.

In some examples, a method of an electronic device including a pluralityof modules is disclosed. The method may include: receiving a first powerrequest for a first module of the plurality of modules; receiving asecond power request for a second module of the plurality of modules;assigning a first power budget to the first module; assigning a secondpower budget to the second module based on the first power budget; anddrawing power at the first module based on the first power budget, andat the second module based on the second power budget. Additionally oralternatively to one or more of the above examples, the method mayfurther include: assigning a first priority to the first module and asecond priority to the second module, wherein assigning the second powerbudget may be further based on the first and second priorities.Additionally or alternatively to one or more of the above examples, thefirst power budget may be assigned before the second power budget, andthe method may further include reducing the first power budget based ona determination that the second priority is higher than the firstpriority. Additionally or alternatively to one or more of the aboveexamples, reducing the first power budget may include: notifying thefirst module that the first power budget has been revoked; and reducingpower to the first module, wherein the second power budget may beassigned only after the power to the first module has been reduced.Additionally or alternatively to one or more of the above examples, thefirst priority may be assigned with respect to a particularfunctionality of the first module. Additionally or alternatively to oneor more of the above examples, the method may further include:determining that the first power request is associated with auser-initiated task, wherein the first priority may be assigned based onthe determination that the first power request is associated with auser-initiated task. Additionally or alternatively to one or more of theabove examples, the method may further include: receiving a third powerrequest for a third module of the plurality of modules; and denying thethird power request based on the first and second power budgets.Additionally or alternatively to one or more of the above examples,assigning the first power budget to the first module may be based on acharge level of a battery of the electronic device. Additionally oralternatively to one or more of the above examples, the electronicdevice may include a power supply, and the method may further include:obtaining a first characteristic of the power supply; and determiningthat the first characteristic is lower than a first threshold; whereinthe first power budget may be assigned to the first module based on thedetermination that the first characteristic is lower than the firstthreshold. Additionally or alternatively to one or more of the aboveexamples, the first power budget may be assigned to the first modulebased on the relationship between the first characteristic and the firstthreshold over time.

In some examples, a method of an electronic device including a powersupply and a first module is disclosed. The method may include:obtaining a voltage level of the power supply; determining that thevoltage level is lower than a first threshold; and in accordance with adetermination that the voltage level is lower than the first threshold,modifying a state of the first module. Additionally or alternatively toone or more of the above examples, the method may further include:determining that the voltage level is lower than a second threshold,lower than the first threshold; and in accordance with a determinationthat the voltage level is lower than the second threshold, powering offthe device. Additionally or alternatively to one or more of the aboveexamples, modifying the state may include preventing the first modulefrom drawing power for a predefined period of time. Additionally oralternatively to one or more of the above examples, modifying the statemay include changing a mode of the first module for a predefined periodof time.

In some examples, a non-transitory computer readable storage mediumstoring one or more programs is disclosed. The one or more programs mayinclude instructions, which when executed by an electronic deviceincluding a plurality of modules, cause the electronic device to performa method including: receiving a first power request for a first moduleof the plurality of modules; receiving a second power request for asecond module of the plurality of modules; assigning a first powerbudget to the first module; assigning a second power budget to thesecond module based on the first power budget; and drawing power at thefirst module based on the first power budget, and at the second modulebased on the second power budget. Additionally or alternatively to oneor more of the above examples, the method may further include: assigninga first priority to the first module and a second priority to the secondmodule, wherein assigning the second power budget may be further basedon the first and second priorities. Additionally or alternatively to oneor more of the above examples, the first power budget may be assignedbefore the second power budget, and the method may further includereducing the first power budget based on a determination that the secondpriority is higher than the first priority. Additionally oralternatively to one or more of the above examples, reducing the firstpower budget may include: notifying the first module that the firstpower budget has been revoked; and reducing power to the first module,wherein the second power budget may be assigned only after the power tothe first module has been reduced. Additionally or alternatively to oneor more of the above examples, the first priority may be assigned withrespect to a particular functionality of the first module. Additionallyor alternatively to one or more of the above examples, the method mayfurther include: determining that the first power request is associatedwith a user-initiated task, wherein the first priority may be assignedbased on the determination that the first power request is associatedwith a user-initiated task. Additionally or alternatively to one or moreof the above examples, the method may further include: receiving a thirdpower request for a third module of the plurality of modules; anddenying the third power request based on the first and second powerbudgets. Additionally or alternatively to one or more of the aboveexamples, assigning the first power budget to the first module may bebased on a charge level of a battery of the electronic device.Additionally or alternatively to one or more of the above examples, theelectronic device may include a power supply, and the method may furtherinclude: obtaining a first characteristic of the power supply; anddetermining that the first characteristic is lower than a firstthreshold; wherein the first power budget may be assigned to the firstmodule based on the determination that the first characteristic is lowerthan the first threshold. Additionally or alternatively to one or moreof the above examples, the first power budget may be assigned to thefirst module based on the relationship between the first characteristicand the first threshold over time.

In some examples, a non-transitory computer readable storage mediumstoring one or more programs is disclosed. The one or more programs mayinclude instructions, which when executed by an electronic deviceincluding a power supply and a first module, cause the electronic deviceto perform a method including: obtaining a voltage level of the powersupply; determining that the voltage level is lower than a firstthreshold; and in accordance with a determination that the voltage levelis lower than the first threshold, modifying a state of the firstmodule. Additionally or alternatively to one or more of the aboveexamples, the method may further include: determining that the voltagelevel is lower than a second threshold, lower than the first threshold;and in accordance with a determination that the voltage level is lowerthan the second threshold, powering off the device. Additionally oralternatively to one or more of the above examples, modifying the statemay include preventing the first module from drawing power for apredefined period of time. Additionally or alternatively to one or moreof the above examples, modifying the state may include changing a modeof the first module for a predefined period of time.

In some examples, an electronic device is disclosed. The electronicdevice may include: one or more processors; memory; a plurality ofmodules; and one or more programs, wherein the one or more programs maybe stored in the memory and configured to be executed by the one or moreprocessors, which when executed by the one or more processors, cause theelectronic device to perform a method including: receiving a first powerrequest for a first module of the plurality of modules; receiving asecond power request for a second module of the plurality of modules;assigning a first power budget to the first module; assigning a secondpower budget to the second module based on the first power budget; anddrawing power at the first module based on the first power budget, andat the second module based on the second power budget. Additionally oralternatively to one or more of the above examples, the method mayfurther include: assigning a first priority to the first module and asecond priority to the second module, wherein assigning the second powerbudget may be further based on the first and second priorities.Additionally or alternatively to one or more of the above examples, thefirst power budget may be assigned before the second power budget, andthe method may further include reducing the first power budget based ona determination that the second priority is higher than the firstpriority. Additionally or alternatively to one or more of the aboveexamples, reducing the first power budget may include: notifying thefirst module that the first power budget has been revoked; and reducingpower to the first module, wherein the second power budget may beassigned only after the power to the first module has been reduced.Additionally or alternatively to one or more of the above examples, thefirst priority may be assigned with respect to a particularfunctionality of the first module. Additionally or alternatively to oneor more of the above examples, the method may further include:determining that the first power request is associated with auser-initiated task, wherein the first priority may be assigned based onthe determination that the first power request is associated with auser-initiated task. Additionally or alternatively to one or more of theabove examples, the method may further include: receiving a third powerrequest for a third module of the plurality of modules; and denying thethird power request based on the first and second power budgets.Additionally or alternatively to one or more of the above examples,assigning the first power budget to the first module may be based on acharge level of a battery of the electronic device. Additionally oralternatively to one or more of the above examples, the electronicdevice may include a power supply, and the method may further include:obtaining a first characteristic of the power supply; and determiningthat the first characteristic is lower than a first threshold; whereinthe first power budget may be assigned to the first module based on thedetermination that the first characteristic is lower than the firstthreshold. Additionally or alternatively to one or more of the aboveexamples, the first power budget may be assigned to the first modulebased on the relationship between the first characteristic and the firstthreshold over time.

In some examples, an electronic device is disclosed. The electronicdevice may include: one or more processors; memory; a power supply; afirst module; and one or more programs, wherein the one or more programsmay be stored in the memory and configured to be executed by the one ormore processors, which when executed by the one or more processors,cause the electronic device to perform a method including: obtaining avoltage level of the power supply; determining that the voltage level islower than a first threshold; and in accordance with a determinationthat the voltage level is lower than the first threshold, modifying astate of the first module. Additionally or alternatively to one or moreof the above examples, the method may further include: determining thatthe voltage level is lower than a second threshold, lower than the firstthreshold; and in accordance with a determination that the voltage levelis lower than the second threshold, powering off the device.Additionally or alternatively to one or more of the above examples,modifying the state may include preventing the first module from drawingpower for a predefined period of time. Additionally or alternatively toone or more of the above examples, modifying the state may includechanging a mode of the first module for a predefined period of time.

Although the disclosed examples have been fully described with referenceto the accompanying drawings, it is to be noted that various changes andmodifications will become apparent to those skilled in the art. Suchchanges and modifications are to be understood as being included withinthe scope of the disclosed examples as defined by the appended claims.

1. (canceled)
 2. A method comprising: at an electronic device includinga first module, a sensor configured to detect presence of a user at theelectronic device, and a power supply: receiving a first power requestfor the first module; determining, using the sensor, whether a user ispresent at the electronic device; assigning a respective power budget tothe first module based on the determination of whether the user ispresent at the electronic device, wherein: in accordance with adetermination that the user is present at the electronic device, therespective power budget is a first respective power budget, and inaccordance with a determination that the user is not present at theelectronic device, the respective power budget is a second respectivepower budget, different than the first respective power budget; anddrawing power at the first module based on the respective power budget.3. The method of claim 2, wherein determining that the user is presentat the electronic device corresponds to the electronic device being in apocket of the user.
 4. The method of claim 2, wherein determining thatthe user is present at the electronic device corresponds to theelectronic device being on an arm of the user.
 5. The method of claim 2,wherein determining that the user is present at the electronic devicecorresponds to the electronic device being in a hand of the user.
 6. Themethod of claim 2, wherein the sensor comprises a light sensor.
 7. Themethod of claim 2, wherein the sensor comprises a heat sensor.
 8. Themethod of claim 2, wherein the sensor comprises a motion sensor.
 9. Themethod of claim 2, wherein the sensor comprises a touch sensor.
 10. Themethod of claim 2, wherein the second respective power budget is lessthan the first respective power budget.
 11. The method of claim 2,wherein the first module comprises a haptic feedback module.
 12. Anelectronic device comprising: a first module; a sensor configured todetect presence of a user at the electronic device; a power supply; oneor more processors; and memory storing one or more instructions, whichwhen executed by the one or more processors, cause the electronic deviceto perform a method comprising: receiving a first power request for thefirst module; determining, using the sensor, whether a user is presentat the electronic device; assigning a respective power budget to thefirst module based on the determination of whether the user is presentat the electronic device, wherein: in accordance with a determinationthat the user is present at the electronic device, the respective powerbudget is a first respective power budget, and in accordance with adetermination that the user is not present at the electronic device, therespective power budget is a second respective power budget, differentthan the first respective power budget; and drawing power at the firstmodule based on the respective power budget.
 13. A non-transitorycomputer readable storage medium storing one or more programs, the oneor more programs comprising instructions, which when executed by anelectronic device including a first module, a sensor configured todetect presence of a user at the electronic device, and a power supply,cause the electronic device to perform a method comprising: receiving afirst power request for the first module; determining, using the sensor,whether a user is present at the electronic device; assigning arespective power budget to the first module based on the determinationof whether the user is present at the electronic device, wherein: inaccordance with a determination that the user is present at theelectronic device, the respective power budget is a first respectivepower budget, and in accordance with a determination that the user isnot present at the electronic device, the respective power budget is asecond respective power budget, different than the first respectivepower budget; and drawing power at the first module based on therespective power budget.